Clickup Mcp

Created By
Marco Pfeiffera year ago
Comprehensive reading capabilities for ClickUp
Overview

What is ClickUp MCP?

ClickUp MCP is a Model Context Protocol server that allows AI assistants to interact with ClickUp tasks, providing comprehensive reading capabilities and task management features.

How to use ClickUp MCP?

To use ClickUp MCP, set up the server with your ClickUp API key and Team ID, and connect it to your AI assistant like Claude, Windsurf, or Cursor.

Key features of ClickUp MCP?

  • Complete access to task information including status and assignees.
  • Full comment history for context.
  • Support for inline images in task descriptions.
  • Task search functionality using keywords.
  • Todo management for listing open tasks.

Use cases of ClickUp MCP?

  1. Retrieve detailed information about specific tasks.
  2. Search for tasks related to specific functionalities.
  3. Manage and check your todo list efficiently.

FAQ from ClickUp MCP?

  • What is required to set up ClickUp MCP?

You need a ClickUp account with API access and your API key and Team ID.

  • Can I use ClickUp MCP with any AI assistant?

Yes, ClickUp MCP is compatible with various AI assistants like Claude, Windsurf, and Cursor.

  • Are there any limitations?

Yes, todo management is limited to 50 tasks, and it does not support browsing ClickUp Lists or Spaces.

Server Config

{
  "mcpServers": {
    "clickup": {
      "command": "npx",
      "args": [
        "-y",
        "@hauptsache.net/clickup-mcp"
      ],
      "env": {
        "CLICKUP_API_KEY": "your_api_key",
        "CLICKUP_TEAM_ID": "your_team_id"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Marco Pfeiffer
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

31 minutes ago